home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The World of Computer Software
/
The World of Computer Software.iso
/
xtrdos.zip
/
XTRDOS.DOC
< prev
next >
Wrap
Text File
|
1992-12-29
|
77KB
|
2,067 lines
Filename: XTRDOS.DOC
Products: Xtrieve PLUS v4.10 and v4.11a for DOS
XQLP v2.11a
XQLPO v2.11a
Date: December 1992
This Readme document accompanies the DOS environment patches for Xtrieve
PLUS v4.10 and v4.11a programs and utilities, the DOS environment patches for
the XQLP v2.11a and XQLPO v2.11a programs, and the optional DOS environment
patches for the XQLP and XQLPO programs.
NOTE: In this document, XQLP and XQLPO are referred to collectively as
XQLP(O).
This patch is cumulative and includes updates for both v4.10 and v4.11. If
you have Xtrieve PLUS v4.10, read this entire document. If you have Xtrieve
PLUS v4.11, read "Installation Procedure" and then skip to "Xtrieve PLUS
v4.11 for DOS."
================================================================================
Disclaimer
==========
Novell, Inc. makes no representations or warranties with respect to any
NetWare software, and specifically disclaims any express or implied
warranties of merchantability, title, or fitness for a particular
purpose.
Distribution of any NetWare software is forbidden without the express
written consent of Novell, Inc. Further, Novell reserves the right to
discontinue distribution of any NetWare software.
Novell is not responsible for lost profits or revenue, loss of use of
the software, loss of data, costs of re-creating lost data, the cost of
any substitute equipment or program, or claims by any party other than
you. Novell strongly recommends a backup be made before any software is
installed. Technical support for this software may be provided at the
discretion of Novell.
PATCH.EXE is a proprietary product of PocketSoft. PATCH.EXE and Patch
Build generated files are distributed by Novell, Inc. under license from
PocketSoft.
Direct Connect and NetWire are service marks of Novell, Inc.
CompuServe is a registered trademark of CompuServe, Incorporated.
================================================================================
Contents
========
Installation Procedure
Patch File Information
Xtrieve PLUS v4.10 for DOS and XQLP(O) v2.11a
Original File Information
Xtrieve PLUS v4.10 Patch Set Descriptions
XQLP v2.11a and XQLPO v2.11a Patch Set Descriptions
XQLP(O) v2.11b Optional Patches
Xtrieve PLUS v4.11 for DOS
Original File Information
Xtrieve PLUS v4.11 Patch Set Descriptions
Documentation Updates
Online Help Updates
================================================================================
Installation Procedure
======================
The PATCHXTR.BAT and PATCH.EXE files mentioned in this procedure require
DOS v2.1 or later.
The Xtrieve PLUS for DOS patch set contains the following:
- This Readme document
- PATCH.EXE, a utility Novell provides for installing product patches
- PATCHXTR.BAT, a batch file to facilitate patch installation
- Patch files for Xtrieve PLUS (XTRIEVE.410 and XTRIEVE.411, which you can
use to patch versions 4.10 or 4.11) and for XQLP (XQLP.21A and XQLPO.21A)
- Replacement files (files with the same names as the files they will
replace)
To update Xtrieve PLUS, complete the following steps:
1. Create a directory on your system, and copy the XTRDOS.ZIP file to
that directory.
2. Use the utility PKUNZIP.EXE to unzip the zipped files.
3. Install the patch files as follows:
a. Refer to the list of patch files in the section "Original File
Information," find the original files on your system, and ensure that
your original files match those listed.
NOTE: Use the original file information specific to the version of
Xtrieve PLUS you are patching.
b. Use the DOS COPY command to copy the original file into the
directory that contains the unzipped patch files from XTRDOS.ZIP.
c. Run PATCHXTR and specify the parameter for the version of Xtrieve
PLUS you want to patch. For example, to patch Xtrieve PLUS v4.10,
enter PATCHXTR 410. (Entering PATCHXTR without any parameters
displays a usage screen that lists all the parameters.)
PATCHXTR verifies that you are patching the original released version
of the software, applies the patch, and gives the original file an
.ORG extension.
d. Use the DOS COPY command to copy the patched file back to the
original file's directory.
4. Install the replacement files as follows:
a. Find the directory that contains the original files to be
replaced.
b. Before copying the replacement files, back up the original files
to a diskette or to another directory.
c. Use the COPY command to replace the original files with the
new files.
5. After applying the patches, you can remove the directory you created to
store the XTRDOS.ZIP file. You may also want to verify the version
numbers when you load each program. The version numbers should match
those listed in the next section, "Patch File Information."
IMPORTANT: If you patched v4.10, your current version of Xtrieve PLUS is
v4.11. When you are ready to patch v4.11, perform Steps 4
through 6 again, using the information provided for Xtrieve PLUS
v4.11.
================================================================================
Patch File Information
======================
Patch Set Filename: XTRDOS.ZIP
Date: 12-29-92
Files Included: XTRDOS DOC This document
PATCH EXE 76981 1-30-92 5:00a
PATCHXTR BAT 3928 12-17-92 3:55p
XQLOPT ZIP 26582 9-22-92 12:08p
(Patch files) XTRDOS 410 v4.11 146529 9-18-92 2:42p
XTRDOS 411 v4.11b 69874 12-17-92 10:43a
XQLP 21A v2.11b 270 9-21-92 1:54p
XQLPO 21A v2.11b 269 9-21-92 1:55p
(Replacement files) MAKE_XTA EXE v4.11b 68768 12-08-92 7:09p
XCFP EXE v4.11b 44624 12-08-92 7:30p
XMENU EXE v4.11b 98960 12-08-92 7:28p
XTRIEVE MSG 39018 12-08-92 5:06p
XTRIEVE HLP 221184 3-20-92 5:55p
XHFP EXE v4.11b 16672 12-08-92 7:29p
XTRIEVE MEN v4.11b 13347 12-08-92 5:06p
================================================================================
Xtrieve PLUS v4.10 for DOS and XQLP(O) v2.11a
=============================================
The following information pertains to the DOS environment patches for
the Xtrieve PLUS v4.10 and XQLP(O) v2.11a programs and utilities.
Original File Information
-------------------------
To ensure you are patching the original files, compare the files to be
patched with those in the following list. This list shows the byte size and
the date and time stamps for the original release.
Patch this file:
XTRIEVE EXE v4.10 454848 8-14-91 11:23a
Replace these files:
XQLP EXE v2.11a 204752 8-18-91 1:34p
XQLPO EXE v2.11a 223936 8-18-91 1:40p
MAKE_XTA EXE v4.10 65712 7-16-91 7:20p
XCFP EXE v4.10 44032 7-17-91 9:19a
XMENU EXE v4.10 98912 7-16-91 8:28p
XHFP EXE v4.10 16672 7-17-91 9:29a
XTRIEVE MSG 38204 8-07-92 3:54p
XTRIEVE HLP 211968 8-07-92 3:54p
XTRIEVE MEN v4.10 13325 8-07-92 3:54p
Xtrieve PLUS v4.10 Patch Set Descriptions
-----------------------------------------
The following information pertains to the DOS environment patches for
the Xtrieve PLUS v4.10 program. This section describes each patch in the
patch set.
For each patch, the description includes one or more search strings. These
search strings indicate areas in which you may encounter the problem that the
patch addresses. The search strings may help you quickly determine whether
the patch you need for a specific problem is included in this patch set.
NOTE: In some cases, the text describes a problem or reported bug that the
update does NOT fix. In those cases, use the workaround provided.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: FOOTERS, HEADERS, REPORT
Problem Fixed by This Patch:
This patch prevents Xtrieve PLUS report headers or footers with more
than one line from overwriting each other.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: FILE_CREATION, PAGE, PREALLOC
Problem Fixed by This Patch:
Xtrieve PLUS uses the default page size (512 KB) if you selected the
Review Definitions option before selecting Finished-Create. In this
situation, Xtrieve PLUS may also fail to preallocate the specified
number of pages. This patch ensures that Xtrieve PLUS uses the page
size you specify, and also that Xtrieve PLUS preallocates the specified
number of pages.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: BFLOAT, DISPLAY, FLOAT, MASK
Problem Fixed by This Patch:
This patch ensures that Xtrieve PLUS can redisplay the proper field
values when a display mask is used for a field of type float/bfloat.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: SDF, TIME, TRANSLATE
Problem Fixed by This Patch:
This patch ensures that Xtrieve PLUS correctly translates time values to
Standard Data Format (SDF).
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: GROUP, HANG, LOCK UP, MODIFY, NESTED
Problem Fixed by This Patch:
When a report contains nested groups, attempting to modify or remove
the outer group's fields when no fields are defined causes the computer
to lock up. This patch prevents the computer from locking up when you
modify or remove fields within the outermost group.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: HANG, LOCK UP, RIGHTS, SECURITY
Problem Fixed by This Patch:
Your computer may lock up in the following situation: you have security
installed on your dictionary files and are using the NetWare SQL
Requester (NSREQ) to access your files, and you attempt to access
file- or field-level rights for a user profile. This patch prevents the
computer from locking up when you access the file- or field-level
rights.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: PRINT, REPORT
Problem Fixed by This Patch:
A report may contain inaccurate information if any line in the report
(except for the last line on the page) is exactly the width of the page.
This patch ensures that the report contains accurate information.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: BIT, DEFINITIONS, OFFSET, PRINT
Problem Fixed by This Patch:
If a file definition includes several bit data type fields adjacent to
each other, a file definition printout shows each bit field starting at
a new offset. This patch corrects the placement of the bit fields.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: 25-LINE, BLANK, CHARACTERS, SCREEN, VGA
Problem Fixed by This Patch:
The following situations can occur in 25-line mode on a VGA monitor
after you exit Xtrieve PLUS:
- The screen goes blank, but you can still enter characters at the
keyboard.
- Keyboard characters are displayed as different characters on the
screen.
This patch prevents either of these conditions from occurring.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: EDIT, HEADING, MODIFY, TITLE
Problem Fixed by This Patch:
If you press Esc and then select Continue when editing or modifying a
view with a defined title field, the title data and heading may
disappear. If you refresh the screen, the data reappears, but not the
heading. This patch corrects the problem, so that both the title data
and heading are retained.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: EDIT, DISPLAY, STRING
Problem Fixed by This Patch:
When you are entering data into a file with several string fields, any
data you enter in the second field does not appear on the screen when
you move to the following field, although the data is actually present
in the Btrieve file. This patch allows the data in the second field to
appear as entered.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: RECALL, REPORT, STORE
Problem Fixed by This Patch:
If you create (or recreate) a view, you must first store and recall it
before you can create and store a report for that view; otherwise, you
cannot recall the report after recalling the view. This patch allows
you to create a report based on a view without first storing and
recalling the view.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: CHARACTER, ESCAPE, HEX, REPORT
Problem Fixed by This Patch:
In a report containing an @esc or an @hexXX instruction (in which the
hexadecimal value of XX represents a nonprintable character), Xtrieve
PLUS does not include either the Escape character or the nonprintable
character in the report. This patch causes Xtrieve PLUS to include
these characters in reports.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: CASE, DEFINITION, DUPLICATE, FIELD
Problem Fixed by This Patch:
Xtrieve PLUS does not detect duplicate field names that differ only in
terms of case until you try to complete the file definition with either
Finished-Create or Finished-Don't Create. This patch causes Xtrieve
PLUS to warn you of the duplication when you initially define the
duplicate field.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: HANG, LOCK UP, SECURITY, SHOW, USER
Problem Fixed by This Patch:
Requesting user security information from Xtrieve PLUS can produce the
wrong information. Also, with a dictionary user base of 255 to 500
users, selecting the SECURITY/USER/Show option may cause your computer
to lock up. This patch causes Xtrieve PLUS to display the proper
information and prevents computer lockup.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: 123, 1-2-3, DATE, EXPORT, LOTUS
Problem Fixed by This Patch:
If you export dates to a Lotus 1-2-3 worksheet, dates before 9/17/89 may
appear as negative values. This patch causes those dates to appear as
positive values.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: EDIT, MODIFY, OUT OF LOCAL HEAP SPACE
Problem Fixed by This Patch:
When you attempt to modify the data in a view that is based on a long
restriction, you receive the message "Out of Local Heap Space in
Xtrieve." This patch allows you to modify the data.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: COMMAND FILE, MAKE, OWNER NAME
Problem Fixed by This Patch:
When you press F7 while running a command file in which you are prompted
for an owner name for a particular file, Xtrieve PLUS does not display
the Make option or all of the command files available. This patch
ensures that Xtrieve PLUS displays the Make option and the complete menu
of command files.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: 226, EDIT, REMOVE
Problem Fixed by This Patch:
If you are using the EDIT/Remove option and attempt to select all
records, Xtrieve PLUS returns Status Code 226. This patch enables you
to select all records in that situation.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: ABORT, CONFIRM, RESTRICTION
Problem Fixed by This Patch:
If you press Esc while defining a restriction, Xtrieve PLUS might not
ask you to confirm that you want to abort the restriction definition.
This patch ensures that Xtrieve PLUS asks for confirmation before
proceeding.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: DICTIONARY, HANG, LOCK UP, SHOW, /W
Problem Fixed by This Patch:
If you select Show from the DICTIONARY menu after starting Xtrieve PLUS
with the /W parameter set to 24, your computer locks up. This patch
allows you to select Show in this situation.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: CONFIGURE, FONT, PRINT, REPORT, STYLE
Problem Fixed by This Patch:
Xtrieve PLUS uses the default font (Courier 10 pitch) if you select a
proportional font or a downloaded font with the Style option of the
CONFIGURE/PRINT menu. This patch ensures that Xtrieve PLUS prints your
report using the font you specify.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: INDEX, OWNER NAME, SUPPLEMENTAL
Problem Fixed by This Patch:
This patch ensures you can define a supplemental index for a file that
has a Btrieve owner name.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: BLANK, DATE, SDF, TRANSLATE
Problem Fixed by This Patch:
When translating data from SDF, Xtrieve PLUS replaces each blank date
( / / ) with the date from the preceding record. This patch ensures
that Xtrieve PLUS properly translates blank dates.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: BTRIEVE, DICTIONARY, FIELD, SHOW
Problem Fixed by This Patch:
If your dictionary definition does not match the Btrieve file
definition, Xtrieve PLUS displays incorrect field information when you
use the DICTIONARY/Show option to examine the file's dictionary
definition. This patch ensures that Xtrieve PLUS properly displays the
field information
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: DATE, MASK, SDF, TRANSLATE, YEAR
Problem Fixed by This Patch:
When translating to Standard Data Format (SDF), Xtrieve PLUS translates
date fields with a mask of mm/dd/yyyy as mm/dd/yy. When translating
four-digit year masks from SDF, Xtrieve PLUS repeats the first two
digits of the year. (For example, it translates 1992 as 1919.) This
patch ensures that Xtrieve PLUS properly translates date fields to
and from of SDF.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: INDEX, JOIN, SEMICOLON, GARBAGE
Problem Fixed by This Patch:
Xtrieve PLUS displays graphic characters at the bottom of the screen
when joining two files on an index that contains a semicolon (;). This
patch enables Xtrieve PLUS to join files in this situation without
displaying extraneous characters.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: LOGICAL, MASK, SDF, TRANSLATE, Y-N
Problem Fixed by This Patch:
When Xtrieve PLUS translates a logical type field with a mask of y-n to
SDF, it translates all values as n. This patch ensures that Xtrieve
PLUS properly translates the data.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: DIVIDE OVERFLOW, PRINT, REPORT
Problem Fixed by This Patch:
When you attempt to print a report to either a file or a printer,
Xtrieve PLUS returns the message "Divide Overflow." This patch allows
you to print a report to a file or a printer.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: 249, RECALL, STORE, VIEW
Problem Fixed by This Patch:
If you attempt to recall a view when more than 249 views are stored in
VIEW.DDF, Xtrieve PLUS returns the message "There Are No Views Stored in
This Dictionary." This patch allows you to recall a view in this
situation.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: 228, COMMAND FILE, EDIT, FPROMPT
Problem Fixed by This Patch:
When attempting to execute the FPROMPT command in a command file,
Xtrieve PLUS recalls the view to be edited but then returns Status Code
228 when you attempt to edit a field. Also, Xtrieve PLUS displays
incorrect data in the field. This patch ensures that Xtrieve PLUS
properly executes the FPROMPT command in command files.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: 1-2-3, LOTUS, REPORT, TIME, TRANSLATE
Problem Fixed by This Patch:
Xtrieve PLUS does not translate fields of data type time from reports
to Lotus 1-2-3 worksheets. This patch ensures that Xtrieve PLUS
can properly translate reports containing time fields to Lotus 1-2-3.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: FIELD NAME, JOIN
Problem Fixed by This Patch:
This patch ensures that Xtrieve PLUS properly joins files that contain
identical field names.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: 209, DICTIONARY, FILE, MODIFY, SECURITY
Problem Fixed by This Patch:
If you attempt to use the SECURITY/MODIFY/File option when there are no
data files defined and the SWITCHES/DICTIONARY/Show option is set to No,
Xtrieve PLUS returns Status Code 209 instead of the error message
"Dictionary is Empty." This patch ensures that Xtrieve PLUS returns the
correct error message in this situation.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: ERROR WRITING OUTPUT, SDF, TRANSLATE, USER-DEFINED,
ZSTRING
Problem Fixed by This Patch:
Xtrieve PLUS returns the message "Error Writing Output" when you
attempt to translate a user-defined field of type zstring (using
Left Chars or Right Chars function) to SDF. This patch ensures that
Xtrieve PLUS properly translates zstring fields to SDF.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: 81, BROWSE, EDIT, HANG, LOCK UP, MODIFY
Problem Fixed by This Patch:
When you return to Browse mode from EDIT/Modify mode, Xtrieve PLUS does
not release the multiple-record locks; consequently, Xtrieve PLUS
returns Status Code 81 (Lock Error) the next time you attempt to switch
to EDIT/Modify mode. This patch ensures that Xtrieve PLUS releases
multiple-record locks when you return to Browse mode from EDIT/Modify
mode.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: HANG, JOIN, KEY, LOCK UP, PRIMARY
Problem Fixed by This Patch:
When you are joining two large files, basing the join on more than one
primary field causes you computer to lock up. This patch ensures you
can join files in this situation.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: GLOBAL, OUT OF LOCAL HEAP SPACE, RIGHTS, SECURITY,
USER
Problem Fixed by This Patch:
When you add a user with global rights only, show that user's rights,
press Esc, and then press F7 to record a command file, Xtrieve PLUS
returns the message "Out of Local Heap Space in Xtrieve." This patch
ensures you can perform this operation without receiving an error.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: COMMAND FILE, OUT OF LOCAL HEAP SPACE, SHIFT-F1
Problem Fixed by This Patch:
When you replay a command file and then press Shift-F1 to select
another command file to replay, Xtrieve PLUS returns the message "Out of
Local Heap Space in Xtrieve." This patch ensures you can perform this
operation without receiving an error message.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: DISPLAY, JOIN, TRUNCATE, VIEW
Problem Fixed by This Patch:
If you join several views together, return to the MAIN menu, and then
access the view you created, Xtrieve PLUS truncates the list of joined
views at the top of your view screen. This patch ensures that Xtrieve
PLUS properly displays the list of joined views.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: DISPLAY, FIELD, SORT, USER-DEFINED, VIEW
Problem Fixed by This Patch:
If your sort is based on a user-defined field, Xtrieve PLUS incorrectly
displays the field by which your view is sorted in the upper right
corner of the definition window. This patch ensures that Xtrieve PLUS
displays this information correctly.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: CONFIGURATION, HANG, LOCK UP, LOG IN, MASTER
Problem Fixed by This Patch:
If you use the Configuration option to log in as a different user after
logging in as MASTER, your computer locks up. This patch allows you to
perform this operation without locking up your computer.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: 284, ADD, CLEAR, FIELD, RECORD
Problem Fixed by This Patch:
If you attempt to add a record without one of the required fields,
Xtrieve PLUS returns Status Code 284 and then clears all the information
you entered. This patch ensures that Xtrieve PLUS does not clear the
information you entered.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: 284, ATTRIBUTE, ERROR WRITING OUTPUT, TRANSLATE, VIEW
Problem Fixed by This Patch:
If you attempt to translate the current view to a retained view with an
invalid field attribute, Xtrieve PLUS returns the message "Error Writing
Output" instead of Status Code 284. This patch ensures that Xtrieve
PLUS returns Status Code 284 in this situation.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: 99/, ADD, EDIT, INTEGER, MASK, RANGE
Problem Fixed by This Patch:
If you use the EDIT/Add option to enter data into an integer field with
the mask 99/ and a range of '1'..'12', Xtrieve PLUS does not accept any
entry in that field. This patch ensures that Xtrieve PLUS allows you
to enter data in this situation.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: BROWSE, EDIT, FORM, OFFSET, REMOVE
Problem Fixed by This Patch:
Xtrieve PLUS does not correctly format data when you use the
EDIT/Remove option following a FORM/Browse operation. This patch
ensures that Xtrieve PLUS displays data at the correct offset.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: HANG, LOCK UP, MENU, OPERATOR, RESTRICTION,
USER-DEFINED
Problem Fixed by This Patch:
Xtrieve PLUS locks up your workstation if you attempt to use a
user-defined menu containing restriction operators that are longer
than those supplied with Xtrieve PLUS. This patch ensures that you
can use such a menu.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: CONDITIONAL, HANG, LOCK UP, FIELD, JOIN, NESTED,
USER-DEFINED
Problem Fixed by This Patch:
If you create a nested, conditional, user-defined field in a joined
view, your computer locks up. This patch ensures that Xtrieve PLUS
returns the error message "Out of Local Heap Space in Xtrieve" instead
of locking up your computer.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: 51, ENCRYPT, INVALID OWNER, OWNER NAME, SUPPLEMENTAL
Problem Fixed by This Patch:
If you add a supplemental index to an encrypted Btrieve file that
requires an owner name for any access (ENCRYPT/Any), Xtrieve PLUS
returns Status Code 51 (Invalid Owner). This patch ensures you can
perform this operation without receiving Status Code 51.
* * * * * * * * *
Platform/Product: DOS - XTRIEVE.EXE, v4.10
Search Strings: CENTER, JUSTIFY, RIGHT
Problem Fixed by This Patch:
This patch ensures that you can right justify a field after you have
center justified it.
* * * * * * * * *
Platform/Product: DOS - MAKE_XTA.EXE, v4.10
Search Strings: HANG, LOCK UP, MAKE_XTA, TRANSLATE, LARGE VIEWS
Problem Fixed:
If you attempt to use the MAKE_XTA utility to translate fields of large
views, your computer locks up. This update ensures you can perform
this operation.
* * * * * * * * *
Platform/Product: DOS - MAKE_XTA.EXE, v4.10
Search Strings: JOIN, MAKE_XTA, TRANSLATE
Problem Fixed by This Patch:
This update ensures that the MAKE_XTA utility properly translates joined
views.
* * * * * * * * *
Platform/Product: DOS - MAKE_XTA.EXE, v4.10
Search Strings: MAKE_XTA, RESTRICTION, USER-DEFINED, VIEW
Problem Fixed by This Patch:
This update ensures that the MAKE_XTA utility can recall a view
definition that includes a user-defined field or restriction.
* * * * * * * * *
Platform/Product: DOS - MAKE_XTA.EXE, v4.10
Search Strings: LAYOUT, MAKE_XTA, REPORT, SUMMARY, TRANSLATE,
USER-DEFINED
Problem Fixed by This Patch:
This update ensures that the MAKE_XTA utility properly translates
information from a report layout file with a user-defined summary field.
* * * * * * * * *
Platform/Product: DOS - XCFP.EXE, v4.10
Search Strings: COMMAND FILE, MOUSE, POSDIRECT, WINDOW, XCFP
Problem Fixed by This Patch:
This update ensures that the XCFP command file processor correctly
interprets mouse commands with the window identifier POSDIRECT.
* * * * * * * * *
Platform/Product: DOS - XMENU.EXE, v4.10
Search Strings: MENU, XMENU, XTRIEVE.MEN
Problem Fixed by This Patch:
If you attempt to open XTRIEVE.MEN, the XMENU utility returns the
message, "'XTRIEVE.MEN' File Is Not a Compatible Menu File for Xtrieve."
This update ensures that XMENU recognizes XTRIEVE.MEN as a compatible
menu file.
* * * * * * * * *
XQLP v2.11a and XQLPO v2.11a Patch Set Descriptions
---------------------------------------------------
Platform/Product: XQLP for DOS - XQLP.EXE, v2.11a
XQLPO for DOS - XQLPO.EXE, v2.11a
Search Strings: FETCH, CURRENT
Problem Fixed by This Patch:
xFetch/XQLFetch CURRENT operations can skip the current record and
return the next record that meets the restriction if the restriction is
in the following format:
"field = 'value' OR field = 'value' OR...."
This patch ensures that xFetch/XQLFetch CURRENT operations return the
current record in this situation.
* * * * * * * * *
Platform/Product: XQLP for DOS - XQLP.EXE, v2.11a
XQLPO for DOS -XQLPO.EXE, v2.11a
Search Strings: QUERY, TABLE, ALTER, HANG, LOCK UP
Problem Fixed by This Patch:
The workstation may hang when XQL attempts to execute a query against a
view and then the tables used to create the view are altered. That is,
the tables are defined, a view is created on the tables, the tables are
altered, and the view (which is no longer applicable) is used, causing
XQL to hang the workstation. This patch prevents the workstation from
locking up.
* * * * * * * * *
Platform/Product: XQLP for DOS - XQLP.EXE, v2.11a
XQLPO for DOS -XQLPO.EXE, v2.11a
Search Strings: 3, GLOBAL DATA VARIABLE
Problem Fixed by This Patch:
If the record length of the first table in a view is greater than 2062
bytes, XQL may overwrite global data variables. One possible symptom of
this problem is that Btrieve returns Status Code 3 when XQL tries to
access the dictionary files. This patch prevents XQL from overwriting
global data variables in this situation.
* * * * * * * * *
Platform/Product: XQLP for DOS - XQLP.EXE, v2.11a
XQLPO for DOS -XQLPO.EXE, v2.11a
Search Strings: XREMALL, REJECT
Problem Fixed by This Patch:
If the reject count passed to xRemall is not -1, and xRemall returned
because the maximum reject count was reached, your application may
enter an infinite loop. Depending on the restriction and the contents
of the data file, xRemall may continue to reject the same set of records
without returning an end-of-file status. This patch prevents your
application from entering an infinite loop in this situation.
* * * * * * * * *
XQLP(O) v2.11b Optional Patches
-------------------------------
Optional patches are available for XQLP(O) v2.11b. These patches can
only be applied after the 2.11a patch set has been applied to the
original 2.11a version of XQLP(O).
These patches can be found in XQLOPT.ZIP, included with this patch set.
================================================================================
Xtrieve PLUS v4.11 for DOS
==========================
The following information pertains to the DOS environment patches for
the Xtrieve PLUS v4.11 programs and utilities.
Original File Information
-------------------------
To ensure you are patching or replacing the original files, compare the files
to be patched or replaced with those in the following list. This list shows
the byte size and the date and time stamps for the original release.
Patch this file:
XTRIEVE EXE v4.11 454848 8-14-91 11:23a
Replace these files:
MAKE_XTA EXE v4.11 65712 7-16-91 7:20p
XCFP EXE v4.11 44032 7-17-91 9:19a
XMENU EXE v4.11 98912 7-16-91 8:28p
XTRIEVE MSG 39017 8-11-92 3:59p
XTRIEVE HLP 221184 3-20-92 5:55p
XHFP EXE v4.11 16672 6-25-92 5:47p
XTRIEVE MEN v4.11 13347 8-11-92 3:59p
Xtrieve PLUS v4.11 Patch Set Descriptions
-----------------------------------------
This section describes each patch in the patch set. For each patch, the
description includes one or more search strings. These search strings
indicate areas in which you may encounter the problem that the patch
addresses. The search strings may help you quickly determine whether the
patch you need for a specific problem is included in this patch set.
NOTE: In some cases, the text describes a problem or reported bug that the
update does NOT fix. In those cases, use the workaround provided.
* * * * * * * * *
Product/Platform: DOS - XTRIEVE.EXE, v4.11
Search Strings: DISPLAY ERRORS
Problem Fixed by This Patch:
In the Report Layout screen, when you insert a field between two fields that
take up a relatively large portion of the screen, Xtrieve PLUS redraws the
screen incorrectly. This patch does not contain a fix; Xtrieve PLUS
accurately stores the new data.
* * * * * * * * *
Product/Platform: DOS - XTRIEVE.EXE, v4.11
Search Strings: F8, HANG, MODIFYING, REPORT LAYOUT
Problem Fixed by This Patch:
When you repeatedly use the key sequence Shift+F8, F8, and Esc when modifying
or viewing groups or fields in a report layout, Xtrieve PLUS terminates.
This patch ensures that Xtrieve PLUS properly closes and reopens the report
layout windows, thus preventing Xtrieve PLUS from terminating.
* * * * * * * * *
Product/Platform: DOS - XTRIEVE.EXE, v4.11
Search Strings: GROUP FIELD, GROUP SUMMARY, REPORT FIELD, REPORT SUMMARY
Problem Fixed by This Patch:
If you use a report field in a report field summary or a group field in a
group field summary, Xtrieve PLUS does not allow you to remove or modify the
field. This patch ensures that Xtrieve PLUS allows you to remove or modify
such fields.
* * * * * * * * *
Product/Platform: DOS - XTRIEVE.EXE, v4.11
Search Strings: FORM/ADD EDIT SCREEN, INVALID RECORD
Problem Fixed by This Patch:
If you attempt to add an invalid record using the Form/Add edit screen,
Xtrieve PLUS exits the Form/Add edit screen and returns to the Form menu.
This patch ensures that if an error occurs when you attempt to add a record,
Xtrieve PLUS remains at the edit screen.
* * * * * * * * *
Product/Platform: DOS - XTRIEVE.EXE, v4.11
Search Strings: REPORT LAYOUT
Problem Fixed by This Patch:
When XQL and Btrieve are loaded by Xtrieve PLUS, report layouts may become
corrupt in memory after you print a report. This patch ensures that Xtrieve
PLUS correctly maintains report layouts.
* * * * * * * * *
Product/Platform: DOS - XTRIEVE.EXE, v4.11
Search Strings: HANG, REMOVE GROUP
Problem Fixed by This Patch:
If you remove a group from a report and then attempt to remove another
group, Xtrieve PLUS displays a repetitive list of groups from which to
choose. In addition, if you choose one of the listed groups, Xtrieve PLUS
causes the workstation to freeze. This patch ensures that Xtrieve PLUS
correctly displays lists of groups.
* * * * * * * * *
Product/Platform: DOS - XTRIEVE.EXE, v4.11
Search Strings: BLANKS, IMPORT DATA, SDF
Problem Fixed by This Patch:
Xtrieve PLUS incorrectly imports data in Standard Data Format (SDF) if
blanks separate the data elements, as in the following example:
"Firstname", "Middlename", "Lastname"
This patch ensures that Xtrieve PLUS correctly imports SDF data.
* * * * * * * * *
Product/Platform: DOS - XTRIEVE.EXE, v4.11
Search Strings: LVAR, NOTE, TRANSLATE, VARIABLE-LENGTH FIELDS
Problem Fixed by This Patch:
Xtrieve PLUS does not correctly process view-to-view translations on
variable-length fields that are not of the same type. For example, you
cannot accurately translate a note field into an lvar field. This patch
ensures that Xtrieve PLUS correctly performs such translations.
* * * * * * * * *
Product/Platform: DOS - XTRIEVE.EXE, v4.11
Search Strings: CREATE FILE, PAGE, PREALLOCATION
Problem Fixed by This Patch:
When you are creating files, Xtrieve PLUS allows you to preallocate no more
than 32,767 pages. This patch ensures that Xtrieve PLUS allows you to
preallocate up to 65,535 pages.
* * * * * * * * *
Product/Platform: DOS - XTRIEVE.EXE, v4.11
Search Strings: BTRIEVE, NEW COMMAND LINE OPTIONS, UNLOAD, XQL
Problem Fixed by This Patch:
Xtrieve PLUS does not unload Btrieve or XQL from memory if you loaded Btrieve
or XQL before you entered Xtrieve PLUS. If you do not have the utilities
BUTIL or NSUTIL, you cannot unload XQL or Btrieve from memory. This patch
makes available two new command line options you can specify when you load
Xtrieve PLUS:
/ua Unloads both XQL and Btrieve when you exit Xtrieve PLUS
/ux Unloads only XQL when you exit Xtrieve PLUS
* * * * * * * * *
Product/Platform: DOS - XTRIEVE.EXE, v4.11
Search Strings: CONDITIONAL, FIELD LIST, SCALAR FUNCTIONS,
USER-DEFINED FIELDS
Problem:
Xtrieve PLUS may not display all available fields in a field list when you
are defining a user-defined field that includes nested conditions or nested
scalar functions, as in the following example expression:
Result = SUBSTRING( SUBSTRING( SUBSTRING( Field3,5,20),2,Field2),5,Field1)
Workaround:
For each level of nesting, create a temporary, user-defined field, as in the
following example:
TempField1 = SUBSTRING( Field3,5,20)
TempField2 = SUBSTRING( TempField1,2,Field2)
TempField3 = SUBSTRING( TempField2,5,Field1)
Since Xtrieve PLUS embeds the temporary field definitions in the substring
field that references it, you can delete the interim temporary fields,
resulting in a single, user-defined field, as in the following example:
Result = TempField3
* * * * * * * * *
Product/Platform: DOS - XTRIEVE.EXE, v4.11
Search Strings: DECIMAL POINTS, INTEGER FIELDS, MASKS
Problem:
If you place a mask that contains decimal points (such as ZZZ,ZZ9.99) on an
integer field, you may get unexpected results in report summary fields. For
example, if the field's data is 38,470.00, the masked result is 384.70.
Workaround:
Masks on integer fields should not contain decimal points. Use a more
appropriate data type, such as decimal, float, money, or numeric.
* * * * * * * * *
Product/Platform: DOS - XTRIEVE.PDB
Search Strings: PRINTER, TABLOID SETTING
Problem:
The Tabloid setting of the XTRIEVE.PDB file specifies the Epson LQ-1500/2.0
printer instead of the IBM PC graphics printer.
Workaround:
Change the Tabloid setting as follows.
1. At a DOS workstation, enter SLATE XTRIEVE.PDB.
2. In the SLATE utility, follow these steps to set the Tabloid setting:
a. Select the Add/Edit Devices (Ptr Connections) option from the main
menu.
b. Select the 3001 Tabloid option from the Devices menu.
c. Use the Tab key to move to the Ptr Mfg field and press F9 to display
a list of printer manufacturers.
d. Select IBM.
e. Use the Tab key to move to the Ptr Type field and press F9 to display
a list of printer types.
f. Select PC Graphics Printer.
3. To exit SLATE, press F10 three times.
* * * * * * * * *
Product/Platform: DOS - MAKE_XTA.EXE, v4.11
Search Strings: 3, HANG, OPEN VIEWS
Problem Fixed by This Patch:
The MAKE_XTA utility hangs or returns Status Code 3 (File Not Open) when you
attempt to open certain views. This patch ensures that MAKE_XTA can open
such views.
* * * * * * * * *
Product/Platform: DOS - MAKE_XTA.EXE, v4.11
Search Strings: FIELD NAMES, LOWERCASE, UPPERCASE
Problem Fixed by This Patch:
The MAKE_XTA utility converts all letters in user-defined field names to
uppercase. This patch ensures that MAKE_XTA preserves lowercase letters in
field names.
* * * * * * * * *
Product/Platform: DOS - MAKE_XTA.EXE, v4.11
Search Strings: EQJOIN, EQUAL, JOIN, KEYWORD, NULL, NULLJOIN
Problem Fixed by This Patch:
The MAKE_XTA utility inserts incorrect keywords in .XTA files that contain
file joins. For example, MAKE_XTA uses the keyword EQUAL when it should use
the keyword EQJOIN. This patch ensures that MAKE_XTA inserts the correct
keywords.
* * * * * * * * *
Product/Platform: DOS - MAKE_XTA.EXE, v4.11
Search Strings: ADD KEYWORD, REPORT LAYOUT, SUM
Problem Fixed by This Patch:
If a report layout contains the calculation type SUM, the MAKE_XTA
utility inserts an extra .ADD. keyword in the XTA file. This patch ensures
that MAKE_XTA inserts the correct number of .ADD. keywords.
* * * * * * * * *
Product/Platform: DOS - MAKE_XTA.EXE, v4.11
Search Strings: BIT FIELDS, CONSECUTIVE FIELDS
Problem Fixed by This Patch:
If a dictionary contains more two or more adjacent fields of type bit, the
MAKE_XTA utility inserts only the first bit field in the .XTA file. This
patch ensures that MAKE_XTA inserts all bit fields.
* * * * * * * * *
Product/Platform: DOS - MAKE_XTA.EXE, v4.11
Search Strings: AUTOINC, INDEX ATTRIBUTES
Problem Fixed by This Patch:
The MAKE_XTA utility incorrectly extracts the index attributes of fields of
type autoinc. This patch ensures that MAKE_XTA retains index attributes as
defined in the original file.
* * * * * * * * *
Product/Platform: DOS - MAKE_XTA.EXE, v4.11
Search Strings: EXTRACT FILES, SUPPLEMENTAL INDEX
Problem Fixed by This Patch:
The MAKE_XTA utility fails when attempting to extract files that contain
supplemental indexes. This patch ensures that MAKE_XTA correctly extracts
supplemental indexes.
* * * * * * * * *
Product/Platform: DOS - MAKE_XTA.EXE, v4.11
Search Strings: DESCRIPTIVE FILENAME
Problem Fixed by This Patch:
If a descriptive filename is shorter than the actual filename, the MAKE_XTA
utility pads the rest of the descriptive filename with characters from the
actual filename. For example, given a descriptive filename of FILE and an
actual filename of TESTING, MAKE_XTA converts the descriptive filename to
FILEING. This patch ensures that MAKE_XTA inserts the correct descriptive
filename into the generated .XTA file.
* * * * * * * * *
Product/Platform: DOS - MAKE_XTA.EXE, v4.11
Search Strings: EXTRACT VIEWS, USER-DEFINED FIELDS
Problem Fixed by This Patch:
The MAKE_XTA utility incorrectly extracts views containing relatively large
user-defined fields. This patch ensures that MAKE_XTA correctly extracts
such views.
* * * * * * * * *
Product/Platform: DOS - XCFP.EXE, v4.11
Search Strings: COMMANDS WITH NUMERALS, PAGE SIZE
Problem Fixed by This Patch:
The Xtrieve PLUS Command File Processor (XCFP) utility does not recognize the
command that specifies page size since the command begins with a numeral.
This patch ensures that XCFP recognizes commands that begin with numerals.
================================================================================
Documentation Updates
=====================
The following sections contain documentation updates for the "Xtrieve
PLUS User's Manual" and the "Xtrieve PLUS Tutorial."
NOTE: The documentation updates that follow are in addition to any
documentation updates noted in the Readme file of the original
product.
Note the following changes to the "Xtrieve PLUS User's Manual":
- Page vi: Replace the section "Where To Get Help" with the following.
Where To Get Help
Novell offers support through a wide range of programs. This section
lists sources of help that are available for the Novell Database
Products line.
Telephone Technical Support
Novell's telephone technical support program provides helpful
information about getting the best results from your Novell product.
Refer to the section "Contacting Novell" for information about
contacting Novell for technical support. If you are contacting
Novell for a follow-up on a previous technical support issue, please
be ready to provide your open call reference number.
International Technical Support
International customers may find the Direct Connect (SM) Fax
International program useful. This program provides priority
handling of fax support, which allows international customers to
obtain technical support without worrying about high telephone costs
and time zone differences. Novell encourages customers who reside
outside the continental United States and Canada to contact their
local Novell office or Novell authorized reseller for more
information about international support options. Refer to the
section "Contacting Novell" for the fax number for international
technical support.
Product Information
The Developer Relations department at Novell Austin can provide
information about Novell Database Products, technical support
programs, and the Novell Professional Developers' Program. You can
request detailed product information from the automated fax system or
speak to a trained technician about product announcements, pricing,
compatibility, services, and developer issues.
CompuServe Forum
You can find information about Novell Database Products under the
NetWire section on CompuServe. NetWire provides 24-hour-a-day
electronic information services. You can obtain the most recent
online technical notes, problem reports and fixes, product news, and
other helpful information. You can also post technical questions and
receive answers from our technical support staff.
If you already have a CompuServe account, type GO NOVELL to access
the NetWire section. For information about subscribing to
CompuServe, contact CompuServe, Inc. at 1-800-848-8199
(or 1-614-457-0802 in Ohio or outside the U.S. and Canada).
Contacting Novell
Novell has established a comprehensive services strategy to support
all network users and systems--small or large, domestic or
international. We welcome hearing from you.
The mailing address for Novell Austin is as follows:
Novell, Inc.
5918 W. Courtyard Drive
Austin, Texas 78730-5036
U.S.A.
To contact us by telephone or fax, refer to the following table for
the appropriate number.
For Contact Telephone Fax
------------------------------------------------------------------------
Technical Support Novell Services 1-800-NETWARE 1-512-794-1775
International (1-800-638-9273)
Technical Support or 1-801-429-5588
outside the U.S.
Product Novell Austin 1-800-RED-WORD 1-512-345-7478
Information* Developer (1-800-733-9673)
Relations or 1-512-794-1796
outside the U.S.
General Inquiries Novell Austin 1-512-346-8380 1-512-345-7478
Receptionist
* International customers can contact their local reseller for Novell
Database Products information.
- Page 1-13: Add the following note before the last paragraph of the
section "Using Xtrieve PLUS with Btrieve and XQLP."
Note: The null file handles that are created when Xtrieve PLUS
automatically loads Btrieve and XQLP are not released when you
quit Xtrieve PLUS. Depending on how high you set the FILES
variable in your CONFIG.SYS file, there may not be any DOS file
handles available when you attempt to start another
application. If this condition occurs, you must restart your
computer before you can run another application.
- Page 1-16: Add the following parameter.
/r<y|n> Tells Xtrieve PLUS whether to restore the original VGA
state after the VGA state is changed temporarily.
Some VGA video adapters cause unexpected results when
Xtrieve PLUS attempts to restore the VGA state after it has
been changed. The /rn option tells Xtrieve PLUS not to
restore the original VGA state after the state has been
changed. The /ry option (the default) tells Xtrieve PLUS
to restore the original VGA state.
- Page 1-17: The description of the /w option should read as follows.
Specifies the maximum view width (in bytes) that Xtrieve PLUS allows.
The view width is determined by combining the length of each field
in the view. However, if a field's heading is longer than the field
itself, use the length of the heading in your calculation. You can
specify from 4 to 8,192 bytes. For example, the following parameter
specification allows a view width of up to 256 bytes: /w:256.
If you do not specify this option, Xtrieve PLUS uses a default value of
1,024 bytes. The larger the view width you specify, the fewer records
Xtrieve PLUS can display on the screen at one time.
- Page 1-18: Add the following note after the first paragraph of the
section "Using the /k Option to Read a Keyboard Input File."
Note: If the keyboard input file includes a directory path, use a
double backslash to represent a single backslash. For example,
the path \XTRIEVE\DEMODATA would be represented as
\\XTRIEVE\\DEMODATA in the input file.
- Page 1-19: The first paragraph in the section "Using the MAIN Menu"
should read as follows.
After you start Xtrieve PLUS, the MAIN menu appears on your screen,
as shown in Figure 1.4. If you are using a mouse, a small block
appears in the upper left corner of the screen. This block indicates
the mouse is enabled. Also, the mouse cursor appears in the center
of the screen (not shown in Figure 1.4).
- Page 2-38: The section "Printing Wide Views" should read as follows.
Printing Wide Views
If your view is wider than 80 characters, you cannot print all of it
at one time (unless your printer can handle more than 80 characters
per line). You must perform multiple print operations to print the
view. That is, print the first 80 characters, and then define a new
offset value from the PRINT OPTIONS menu to print subsequent
characters (in groups of 80 characters per print operation).
To print a wide view, proceed as follows:
1. For the first print operation, choose Print from the VIEW menu,
select Yes from the DEFAULTS menu, and enter the device name in
the DEVICE NAME box to send the view to the printer.
2. For the second print operation, choose Print from the VIEW menu.
3. When the DEFAULTS menu appears, select No.
4. When the PRINT OPTIONS menu appears, accept the defaults until you
get to the Offset option. Enter 80 for the offset.
If additional print operations are necessary, repeat Steps 2 through
4, adding 80 to the offset each time until the entire view is
printed.
- Page 3-15: In Table 3-1, the description of a Null join should read
as follows:
Include all records from the primary file even if they have no
matching records with the secondary file.
- Page 3-19: Add the following note to the end of the section
"Translating to an External Format."
Note: If you use the Translate to DIF option to import dates into
Lotus 1-2-3 from a file created by Xtrieve PLUS v4.10 or v4.11,
the dates will be wrong by one day. This is because Xtrieve
PLUS uses the date 01/01/1900 as day 0, whereas Lotus considers
the same date as day 1. To convert the data to the proper
date, use a formula in your Lotus spreadsheet to subtract one
from the date.
- Page 4-6: Add the following note at the end of the section "Absolute
and Relative Positioning."
Note: If the position of the first report item on a page (not
including the heading) is set using absolute line positioning
or using a relative line position of +0, Xtrieve PLUS places
each occurrence of that report item on a new form, even if the
NEW FORM option is set to No.
- Page 4-13: In the last paragraph of the section "The Report Layout
Screen," the sentence that begins "If you press Shift+F8" should read
as follows.
If you press Shift+F8 while the Report Layout screen is displayed in
Prompt mode, you can see the line type for each line (header, detail,
footer) in the left margin, as Figure 4.6 shows.
- Page 5-4: Add the following note before the third bullet.
Note: You cannot assign a mask to a date that prints as a result of
the @date text directive; the date prints using the default
date mask (mm/dd/yy). If you want to apply a mask to the date
in your report, add a user-defined date field to the view on
which your report is based, and specify CURRENT as the field's
definition. This field will always contain the current date.
When you position the field in the report, Xtrieve PLUS asks
you to specify a mask.
- Page 7-24: Add the following note after the first paragraph of the
section "Defining Supplemental Indexes."
Note: You cannot define or remove a supplemental index for a file
that is active in a view. Release the file before attempting
either operation.
- Page 7-24: Step 2 in the section "Defining Supplemental Indexes"
should read as follows.
2. Select the file for which you want to define a supplemental index.
The menu that appears lists three options: Show, Define, and
Remove. (If you select a file that is currently active, the only
option available is Show.)
- Page 7-25: The first paragraph in the section "Removing Supplemental
Indexes" should read as follows.
To remove a supplemental index for a file, complete the following
steps. (Remember, you cannot remove a supplemental index for a file
that is active in a view.)
- Page 7-25: Step 2 in the section "Removing Supplemental Indexes"
should read as follows.
2. Select the file for which you want to remove a supplemental index.
The menu that appears lists three options: Show, Define, and
Remove. (If you select a file that is currently active, the only
option available is Show.)
- Page 10-5: Replace the first sentence after Table 10.1 with the
following.
Xtrieve PLUS supports landscape printing. Refer to the section
"Defining Printer Devices" on page 10-7 for information about
creating a device that allows you to print in landscape mode.
- Page 10-8: Add the following note after Step 6.
Note: Some printer manufacturers list a separate printer type for
landscape printing. For those printer types, the printer
database displays (LS) as part of the type name. Ensure that
you choose the landscape printer type, where appropriate.
- Page 10-8: Add the following note after Step 8.
Note: If you are defining a device that allows you to print in
landscape mode, modify the settings under Paper Setup as
follows:
Paper Length: 8.50 in
Paper Width: 11.00 in
Under Defaults, set the top and bottom margins to a minimum
of .10 inches, and set the left and right margins to a minimum
of .25 inches.
- Page 10-25: Replace the description of the Display Width parameter
in Table 10.4 with the following.
Defines the maximum record width used in a view. The default is
1,024. The maximum allowed is 8,192.
- Page 11-19: The last paragraph in the section "Setting Environment
Variables Using the Set Command" should read as follows.
Replace variable with one of the 11 Xtrieve PLUS environment
variables. Do not insert a space on either side of the equal sign
(=).
If you want to negate a previous setting, issue the SET command
as follows, replacing variable with one of the 11 Xtrieve PLUS
environment variables, but without specifying a value.
SET variable =
The following sections explain how to set each of the Xtrieve PLUS
environment variables with the SET command.
- Page 11-22: Replace the section XTRPATH with the following.
XTRPATH
Xtrieve PLUS searches for your data files in the location specified
in the dictionary, or in the location specified in the dictionary and
the XTRPATH environment variable. Xtrieve PLUS ignores the XTRPATH
variable if the location specified in the dictionary begins with a
backslash (\) or a drive letter, thus enabling you to use the
dictionary alone to specify the complete path to search for the data
files. However, if you need to accommodate different location names
based on users' drive mappings, you should use the XTRPATH
environment variable in conjunction with the dictionary to specify
the data file location.
If you use the XTRPATH variable, ensure that the file location
specified in the dictionary is complementary to the path specified in
XTRPATH. Depending on where you run Xtrieve PLUS, the XTRPATH
variable can be used in a number of ways, as follows:
Data File Location
XTRPATH Specified in Dictionary Comment
-----------------------------------------------------------------
F:\TEST\DATA MYFILE.BTR Works in all cases
\TEST\DATA MYFILE.BTR Works if running
Xtrieve PLUS from F:
TEST\DATA MYFILE.BTR Works if running
Xtrieve PLUS from F:\
To avoid binding users to a particular drive mapping and directory
for their data file location, you should use XTRPATH to specify the
drive and as much of the path as possible, specifying only the
filename in the dictionary. In the preceding example, if the file
MYFILE.BTR resides on F:\TEST\DATA, you should set XTRPATH to
F:\TEST\DATA and specify MYFILE.BTR as the data file location in the
dictionary.
However, in some cases, you may want to specify only part of the path
in XTRPATH. If you intend to store data files in several
subdirectories with the same name but with different paths, specify
the variable portion of the path in XTRPATH; use the dictionary to
specify the subdirectory where the data files reside.
You can also use the XTRPATH variable to instruct Xtrieve PLUS to
search multiple directories for data files. Use a semicolon to
separate the directories. For example, to instruct Xtrieve PLUS to
search the directories F:\DATA and G:\FILES for data files, set
XTRPATH as follows:
SET XTRPATH = F:\DATA;G:\FILES
If you modify XTRPATH from within Xtrieve PLUS and then save the
configuration, Xtrieve PLUS stores the modified value with the
configuration file. However, the value stored in the operating
system environment takes precedence over the value stored in the
configuration file.
- Page A-1: Replace the note in the section "Xtrieve PLUS Error
Messages" with the following.
Note: If the Xtrieve PLUS message file is not available, Xtrieve PLUS
displays the following message:
Xtrieve message file not loaded. Error code = xxxx
In this message, xxxx represents an internal code. If you
receive this message and you want Xtrieve PLUS to display
textual error messages, you can either place the message file
(XTRIEVE.MSG) in the directory from which you started Xtrieve
PLUS or set the XTRMSG environment variable to indicate the
directory that contains the Xtrieve PLUS message file. (For
more information on the XTRMSG environment variable, see
Chapter 11, "Configuring Xtrieve PLUS.") You must restart
Xtrieve PLUS for either of these changes to take effect.
Thereafter, when an error condition occurs, Xtrieve PLUS
displays one of the textual error messages described in this
appendix.
- Page A-4: Add the following message and description.
Dictionary is Empty
Xtrieve PLUS cannot access the dictionary files, or no dictionary
files exist. Either modify the configuration to specify the
location of the dictionary files, or create dictionary files in the
directory where Xtrieve PLUS is configured to find them.
- Page A-7: Add the following message and description.
Error Setting Field Attribute, Status = n
In Xtrieve PLUS, Status Code n was returned when you set a field
attribute.
- Page A-8: Add the following message and description.
File Does Not Have Any Fields which May Be Used in an Index
In Xtrieve PLUS, you have attempted to define an index in a file in
which all of the fields are of the data type bit. A bit type field
cannot be used as an index. Either define a field of a data type
other than bit and then use it in an index, or make the file a
data-only file.
- Page A-10: Add the following message and description.
Insufficient Memory in Xtrieve to Show All Fields
Xtrieve PLUS returns this message when there is not enough memory
available to hold the field definitions you have specified. To make
more memory available, unload any TSRs that are not in use.
Alternatively, if your workstation has expanded or extended memory,
you can use your memory management program to move TSRs or
applications to high memory.
- Page A-10: Add the following message and description.
Invalid Temporary Storage Directory. Directory Must Exist
Xtrieve PLUS used the directory specified in the XTRTMP environment
variable to store temporary files that hold session-specific
information. Either create the directory you specified, or reset the
XTRTMP variable to an existing directory.
- Page A-11: The message "Missing or invalid 'col' specification in
text window file" should read "Missing or Invalid '@xxxxx'
Specification in Text Window File." The explanation of this message
should read as follows.
In Xtrieve PLUS, the specification for the column location, row
location, or width value in the text window file is either invalid or
missing. Correct the value, or supply it if it is missing.
- Page A-12: The message "Missing or Unrecognized Menu Definition
File" should read "Missing or Invalid Menu Definition File." The
explanation of this message should read as follows.
Either Xtrieve PLUS attempted to use an old version of the menu
definition file (XTRIEVE.MEN), or it cannot find the menu definition
file. Ensure that you are using the version of the menu definition
file contained on your Xtrieve PLUS diskettes. Also, this file must
be located in either the current directory or the directory specified
in the configuration file (using the XTRMEN environment variable) as
the location for the menu definition file.
- Page A-12: Add the following message and description.
Money Fields May be from 2 to 10 Bytes Inclusive
In Xtrieve PLUS, you defined a money type field with a size less than
2 or greater than 10. Modify the size of the field so that it is
within the valid range.
- Page A-15: Add the following message and description.
Numeric Fields May be from 1 to 15 Bytes, Inclusive
In Xtrieve PLUS, you defined a numeric type field with a size less
than 1 or greater than 15. Modify the size of the field so that it
is within the valid range.
- Page A-15: Add the following message and description.
Out of File Handles. Increase 'FILES=' Parameter in CONFIG.SYS
Xtrieve PLUS cannot assign a DOS handle to open the file. Increase
the 'FILES=' parameter in the CONFIG.SYS file.
- Page A-17: Add the following message and description.
Please Specify an Integer Value Between 0 and 10, Inclusive
The value specified for the Delay Time option on the
CONFIGURE/PARAMETERS menu tells Xtrieve PLUS how many tenths of a
second to delay when replaying command files. This value must be
an integer between 0 and 10, inclusive.
- Page A-17: Add the following message and description.
Please Specify an Integer Value Between 4 and 8192, Inclusive
In Xtrieve PLUS, the value specified for the Display Width option on
the CONFIGURE/PARAMETERS menu defines the maximum record width used
in a view. This value must be an integer between 4 and 8,192,
inclusive.
- Page A-17: Add the following message and description.
Please Specify an Integer Value Greater than 0
In Xtrieve PLUS, the values specified for the Views, Fields, and
Report Items options on the CONFIGURE/PARAMETERS menu define the
maximum number of active views, the maximum number of active fields
in all views, and the maximum number of report elements in a report,
respectively. For these options, you must specify an integer value
greater than 0.
- Page A-20: Add the following message and description.
The User PUBLIC Cannot Be Removed
In Xtrieve PLUS, you attempted to remove the user PUBLIC by using the
Security option. Since the user PUBLIC is system defined, you cannot
remove it.
- Page A-22: Add the following message and description.
Unable to Drop File Definition, Status = n
In Xtrieve PLUS, you do not have ownership of the file. Determine
the Btrieve owner name and try the operation again.
- Page A-22: Add the following message and description.
Unable to Drop Supplemental Index, Status = n
In Xtrieve PLUS, you do not have ownership of the file for which the
index is defined. Determine the Btrieve owner name and try the
operation again.
- Page A-22: Add the following message and description.
Unable to Open Keyboard Input File
If you entered /k:filename on the command line, Xtrieve PLUS is
unable to find the specified keyboard input file. If you are using
the XTRIEVE.CNF file to implement the /k option, ensure that
XTRIEVE.CNF is not corrupted.
- Page A-24: Add the following message and description.
User Defined Field Cannot Be Added When There Is a Variable-Length
Field
When you are creating a view that includes a variable-length field in
Xtrieve PLUS, the variable-length field must be the last field you
define. Remove the variable-length field, add the user-defined
field, and redefine the variable-length field.
- Page A-24: Add the following message and description.
User Input Is Required, But No Input Source Is Available
In Xtrieve PLUS, you attempted to run a command file that requires
keyboard input, but no keyboard input file is available. Restart
Xtrieve PLUS without using the /d startup option. Alternatively, you
can restart it using the /k startup option and provide a keyboard
input file. (See "Running Xtrieve PLUS" in Chapter 1.)
- Page A-41: Add the following Status Codes and descriptions.
207 Field Does Not Exist in the Dictionary
One of the fields in the list is not defined in the
currently active dictionary. Be sure you specified the
names correctly and you used the appropriate character
representation for a blank if the name contains embedded
blanks.
208 The Position Parameter Value Is Out of Range for This
Function
The position you specified for a field in a field list is
out of range. Valid positions are between 1 and the number
of fields in the view, inclusive.
- Page A-43: Add the following Status Code and description.
227 Operand Must Be a Dictionary Field
The first operand in a restriction statement must be a
valid field that is defined in the dictionary.
- Page A-49: Add the following status codes.
349 The Specified Data Value Is Too Large for the Field Definition
The data value you specified is larger than the maximum length
defined for the field.
350 Security Has Not Been Enabled on This Dictionary
You attempted an operation that you can do only when security is
enabled. Database security is not enabled at this time. To perform
the operation successfully, you must first enable security on that
database.
351 A Transaction Has Not Yet Been Started
You attempted to perform a COMMIT or ROLLBACK operation without being
inside a transaction. You must start a transaction before you can
perform a COMMIT or ROLLBACK operation. To start a transaction,
issue a START TRANSACTION operation.
352 Record Count Must Be Greater Than Zero
NetWare SQL received a record count value for the xFetch call that is
not more than zero. The record count for an xFetch call must be at
least 1.
- Page D-5: The description of Bit 5 of Xi$Flags should read as
follows.
Index is not case sensitive.
- Page E-1: Add the following parameters.
/r<y|n> Tells Xtrieve PLUS whether to retain the current VGA state
when the VGA state is changed temporarily.
/s Identifies the NetWare SQL or XQLP session
- Page E-1: Change the maximum value for the /f parameter from 511 to
N/A; there is no maximum value for this parameter.
Note the following changes to the "Xtrieve PLUS Tutorial":
- Page 3-21: Step 2 of the section "Justifying Data in a View" should
read as follows.
If modifying a field, select the field you want from the MODIFY menu.
If adding a field, select No from the DEFAULTS menu, and then select
the field you want from the ADD menu.
- Page 4-15: In the example given in Step 2 of the section "Browsing a
View," reverse the values for Amt Paid and Balance Due.
- Page 4-18: Step 9 of the section "Creating the Schedule View" should
read as follows.
9. Select the USER DEFINED option, and then select String from the
TYPE menu. Enter 35 for the field size.
================================================================================
Online Help Updates
===================
- Several sections of the help text indicate you can define a maximum
of 119 indexes for a file. Xtrieve PLUS allows only 24 indexes per
file.
- The help text includes several references to the numericsts data
type. However, Xtrieve PLUS does not support this data type.
- In the section of the help text that discusses the Parameters option
on the CONFIGURATION menu, the references to the NetWare SQL
Requester and the NetWare Btrieve Requester should read XQLP and
Btrieve, respectively.
** End of XTRDOS.DOC **